Resource path monitoring

ABSTRACT

Systems and techniques are provided for a resource distribution system. Selected resource paths in a resource transfer network may be monitored. A quantity of an intermediate resource type to transfer into resource pools in the resource transfer network may be determined. Each of the resource pools may be associated with a leg that can be part of a route with two legs for one or more of the selected resource paths. Instructions decrementing a register in a repository resource pool by the determined quantities of the intermediate resource type to be transferred into the resource pools in the resource transfer network and incrementing a register in each of the resource pools in the resource transfer network by the determined quantity of the intermediate resource type to be transferred into that resource pool when the determined quantity is greater than zero may be generated and caused to be executed.

BACKGROUND

Resources may be transferred across various network paths. A first nodein the network may transfer resources to a second node in the network.In some cases, the first node may transfer out a first type of resource,but the second node may only wish to receive a second type of resource.An intermediate may be needed to accept the first type of resource fromthe first of the two nodes and send out the second type of resource tothe second of the two nodes to complete the resource transfer. The pathsbetween the first and second nodes may be go through a limited number ofintermediate nodes, and certain intermediate nodes may only handle thesending or receiving of certain resource types. This may increase thecost of the resource transfer between the two nodes, as the intermediatenodes may impose their own costs on resource transfers that pass throughthem, and there may be a limited number of intermediate nodes to choosefrom.

BRIEF SUMMARY

According to an embodiment of the disclosed subject matter, anindication of an available leg for a resource path may be received. Theresource path may include a front resource type and a back resourcetype. The available leg may be associated with a resource pool includinga register indicating a quantity of an intermediate resource type. Theavailable leg may be used to form a route for half of the resource path.A total quantity of an intermediate resource type transferrable eitherout of or into the resource pool associated with the leg may bedetermined from the indication of the available leg. A quantity of theintermediate resource type to be transferred into the resource poolassociated with the leg may be determined based on the total quantity ofthe intermediate resource type transferrable either out of or intoresource pool associated with the leg. Instructions decrementing aregister in a repository resource pool by the determined quantity of theintermediate resource type to be transferred into the resource poolassociated with the leg and incrementing the register in the resourcepool associated with the leg by the determined quantity of theintermediate resource type to be transferred into the resource poolassociated with the leg may be generated and caused to be executed.

Selected resource paths in a resource transfer network may be monitored.A quantity of an intermediate resource type to transfer into resourcepools in the resource transfer network may be determined. Each of theresource pools may be associated with a leg that can be part of a routewith two legs for one or more of the selected resource paths.Instructions decrementing a register in a repository resource pool bythe determined quantities of the intermediate resource type to betransferred into the resource pools in the resource transfer network andincrementing a register in each of the resource pools in the resourcetransfer network by the determined quantity of the intermediate resourcetype to be transferred into that resource pool when the determinedquantity is greater than zero may be generated and caused to beexecuted.

A computing device may monitor selected resource paths in a resourcetransfer network. The computing device may determine a quantity of anintermediate resource type to transfer into each of a number of resourcepools in the resource transfer network. Each of the resource pools maybe associated with a leg that can be part of a route with two legs forthe selected resource paths. The computing device may generate and causeto be executed instructions decrementing a register in a repositoryresource pool by the determined quantities of the intermediate resourcetype to be transferred into the resource pools in the resource transfernetwork and incrementing a register in each of the resource pools in theresource transfer network by the determined quantity of the intermediateresource type to be transferred into that resource pool when thedetermined quantity is greater than zero.

Systems and techniques disclosed herein may allow for a resourcedistribution system. Additional features, advantages, and embodiments ofthe disclosed subject matter may be set forth or apparent fromconsideration of the following detailed description, drawings, andclaims. Moreover, it is to be understood that both the foregoing summaryand the following detailed description are examples and are intended toprovide further explanation without limiting the scope of the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the disclosed subject matter, are incorporated in andconstitute a part of this specification. The drawings also illustrateembodiments of the disclosed subject matter and together with thedetailed description serve to explain the principles of embodiments ofthe disclosed subject matter. No attempt is made to show structuraldetails in more detail than may be necessary for a fundamentalunderstanding of the disclosed subject matter and various ways in whichit may be practiced.

FIG. 1 shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.

FIG. 2 shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.

FIG. 3 shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.

FIG. 4 shows an example arrangement suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.

FIG. 5A shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.

FIG. 5B shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.

FIG. 6 shows an example arrangement suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.

FIG. 7A shows an example arrangement suitable for a resourcedistribution system according to an implementation of the disclosedsubject matter.

FIG. 7B shows an example arrangement suitable for a resourcedistribution system according to an implementation of the disclosedsubject matter.

FIG. 7C shows an example arrangement suitable for a resourcedistribution system according to an implementation of the disclosedsubject matter.

FIG. 8 shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.

FIG. 9 shows an example arrangement suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.

FIG. 10 shows an example arrangement suitable for a resourcedistribution system according to an implementation of the disclosedsubject matter.

FIG. 11 shows an example arrangement suitable for a resourcedistribution system according to an implementation of the disclosedsubject matter.

FIG. 12 shows an example procedure suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.

FIG. 13 shows a computer according to an embodiment of the disclosedsubject matter.

FIG. 14 shows a network configuration according to an embodiment of thedisclosed subject matter.

DETAILED DESCRIPTION

According to embodiments disclosed herein, a resource distributionsystem may allow for the distribution of resources to resource poolsthat are used that are used to transfer resources across resource types.A resource monitoring system, which may be any suitable computingdevice, may monitor the availability and use of routes along pathsthrough resource tracking systems. The resource tracking systems may beany suitable computing devices for tracking the ownership of resources.The resource monitoring system may cause the transfer of resources to aresource pool on a resource tracking system based on any suitablecriteria, such as how many routes are offered through the resource pool,or the volume of resources that passes through the resource pool.

Resource transfers may involve a change of resource types during thetransfer. Resource pools controlled by an intermediary party may be usedto effect the change of resource type. For example, a source party maywish transfer out a first resource type from a resource pool controlledby the source party, while a sink party may request to receive a secondresource type at a resource pool controlled by the sink party. Aquantity of the first resource type may be sent to a resource poolcontrolled by an intermediary party, which may keep the quantity of thefirst resource type and may transfer out a quantity of the secondresource type from another resource pool controlled by the intermediaryparty to a resource pool controlled by the sink party. There may be acost for the use of the resource pools controlled by the intermediaryparty in the transfer. For example, the quantity of the first resourcetype transferred out by the source party and kept in a resource poolcontrolled by the intermediary party may be greater than the quantity ofthe first resource type that the source party would have transferreddirectly to the resource pool of the sink party had the sink partyrequest the first resource type.

There may be a number of different resource types which can betransferred. For example, a resource may a computational resource suchas processor time, volatile and non-volatile storage space, and networkbandwidth. Resource transfers may take place across resource paths. Aresource path may be a pairing of two resource types, a front resourcetype and a back resource type. For example, a resource path may includea first resource type, which may be the front resource type for theresource path, and a second resource type, which may be the backresource type for the resource path. Resource transfers may take placeacross a resource path with either the front resource type beingtransferred out and the back resource type being transferred in, forminga first half of the resource path, or the back resource type beingtransferred out and the front resource type being transferred in,forming a second half of the resource path.

A resource path may include a number of different routes. A route mayinclude intermediate resource pools, controlled by intermediary parties,through which resources are transferred, and through which a change ofresource types may take place. The intermediate resource pools may allowa source party to have the front resource type for the resource pathtransferred out of its resource pool while the resource pool controlledby the sink party may receive the back resource type for the resourcepath. Different routes may include different intermediary parties. Forexample, a first route for a resource path may include a firstintermediary party, while a second route for the resource path mayinclude a second intermediary party. Some routes may include more thanone intermediary party. The use of an intermediate resource poolcontrolled by an intermediary party in a route may incur a cost.

Routes for a resource path may include legs. Each leg of a route mayinvolve a change from one resource type to another resource type. Thechange may be made through resource pools controlled by intermediaryparties. For example, the completion of a leg may include two sets ofresource transfers using four resource pools on two resource trackingsystems. A first resource type may be transferred out of a firstresource pool and into a second resource pool on a first resourcetracking system. A second resource type may be transferred out of athird resource pool and into a fourth resource pool on a second resourcetracking system, completing the leg. The second and third resource poolsmay be controlled by the same party, which may be, for example, anintermediary party. The second and third resource pools may make up theleg, and may be an incoming resource pool and outgoing resource pool forthe leg. The first resource pool used in completing a leg may be, forexample, a resource pool controlled by a source party that is making useof the leg for a resource transfer to a sink party, or by anotherintermediary party when the leg is not the first leg of route with morethan one leg. The fourth resource pool used in completing the leg maybe, for example, a resource pool controlled by a sink party, or a byanother intermediary party when the leg is not the last leg of a routewith more than one leg. The resource pools for a leg may be on separateresource tracking systems, or may be on the same resource trackingsystem. Every leg may have its own staring resource type and endingresource type. The starting resource type of a leg may be the resourcetype transferred from the first resource pool of the leg to the second,or incoming, resource pool of the leg, and the ending resource type ofthe leg may be the resource type transferred from the third, oroutgoing, resource pool to the fourth resource pool of the leg.

A route for the first half of a resource path may include one leg thatchanges the front resource type for the resource type to the backresource type for the resource path. The starting resource type for theleg may be the same as the front resource type for the resource path,and the ending resource type for the leg may be the same as the backresource type for the resource path. For example, the front resourcetype may be transferred to a resource pool controlled by an intermediaryparty, the incoming resource pool for the leg, from a resource poolcontrolled by the source party. The back resource type may then betransferred from a resource pool controlled by the intermediary party,the outgoing resource pool for the leg, to a resource pool controlled bya sink party, effecting the change of resource type from the frontresource type to the back resource type and completing the resourcetransfer across resource path. Similarly, a route for the second half ofa resource path may include on leg that changes the back resource typefor the resource path to the front resource type for the resource path.

A route for a first half of a resource path may include two legs. Thestarting resource type for the first leg may be the same as the frontresource type for the resource path, and the ending resource type forthe second leg may be the same as the back resource type for theresource path. An intermediate resource type may be the ending resourcetype for the first leg and the starting resource type for the secondleg. To form a route with more than one leg, consecutive legs may needto overlap. The incoming resource pool for a leg may need to be on thesame resource tracking system as the outgoing resource pool for theprevious leg, and both may need to include the intermediate resourcetype, so that the completion of one leg begins the subsequent leg. Forexample, a front resource type may be transferred to a resource poolcontrolled by an intermediary party, the incoming resource pool for thefirst leg, from a resource pool controlled by the source party. Anintermediate resource type may be transferred from a resource poolcontrolled by the intermediary party, the outgoing resource pool for thefirst leg, to a resource pool controlled by a second intermediary party,the incoming resource pool for the second leg, ending the first leg andstarting the second leg. A back resource type may then be transferredfrom a resource pool controlled by the second intermediary party, theoutgoing resource pool for the second leg, to a resource pool controlledby a sink party, ending the second leg and effecting the change ofresource type from the front resource type to the back resource type.This may complete a resource transfer across the resource path using aroute with two legs. Similarly, a route for the second half of aresource path may include two legs, where the staring resource type ofthe first leg is the back resource type for the resource path and theending resource type of the second leg is the front resource type forthe resource path. In some implementations, a route that uses more thanone leg may not have a separate resource pool controlled by a separateintermediary party for each leg. For example, on a route with two legs,a single intermediary party may control a resource pool which may beboth the outgoing resource pool for the first leg and the incomingresource pool for the second leg, as well as the outgoing resource poolfor the second leg out of which the ending resource type is transferred.There may still be separate costs for each leg of the route. A singleresource pool may also be an incoming resource pool for one leg, andoutgoing resource pool for another, separate, leg.

Every leg may have its own associated cost when effecting a change fromone resource type to another resource type. For example, on a route withtwo legs for the first half of a resource path, the cost of the firstleg may be the difference between the quantity of the first leg'sstarting resource type, which may be, for example, the front resourcetype for the resource path, that is transferred from the first resourcepool of the leg to the incoming resource pool of the leg and thequantity of the first leg's starting resource type that could have beentransferred to the first leg's fourth resource pool, the incomingresource pool for the second leg, had the intermediate party controllingthe fourth resource pool accepted the starting resource type. The costof the second leg may be the difference between the quantity of thesecond leg's starting resource type that is transferred from the firstresource pool of the leg, the outgoing resource pool of the first leg,to the second resource pool of the leg, the incoming resource pool ofthe second leg, and the quantity of the second leg's starting resourcetype that could have been transferred to the second leg's fourthresource pool had the sink party controlling the fourth resource poolaccepted the starting resource type for the second leg in place of theending resource type, which may be, for example, the back resource typefor the resource path.

A group of legs that allow resource transfers with changes in resourcetype may form a resource transfer network. The resource transfer networkmay include any number of resource paths, each including any number ofroutes made up of the legs of the resource transfer network. Theresource paths available on a resource transfer network may be based onthe type of resource changes that can be effected by the legs of theresource transfer network. For example, for a resource path with a firstresource type as its front resource type and a second resource type asits back resource type to be available on a resource transfer network,the resource transfer network may need to include either a one-leg ortwo-leg route for each half of the resource path. For the first half ofthe resource path, the resource transfer network may need to includeeither a leg that has the first resource type as its starting resourcetype and the second resource type as its ending resource type, or twolegs, where one of the two legs has the first resource type as itsstarting resource type and an intermediate resource type as its endingresource type and the other of the two legs includes the intermediateresource type as its starting resource type and the second resource typeas its ending resource type. For the second half of the resource path,the resource transfer network may need to include either a leg that hasthe second resource type as its starting resource type and the firstresource type as its ending resource type, or two legs, where one of thetwo legs has the second resource type as its starting resource type andan intermediate resource type as its ending resource type and the otherof the two legs includes the intermediate resource type as its startingresource type and the first resource type as its ending resource type.In some implementations, only either the first half or the second halfof a resource path may be available in a resource transfer network.

The resource transfer network may include a number of resource trackingsystems. A resource tracking system may be any suitable system fortracking resources controlled by various parties, and for transferringresources between parties. A resource tracking system may be anysuitable computing device or system, with any suitable combination ofhardware and software, such as, for example, a system run by a financialinstitution, a hardware or software component of a server system orcomputing device, or a distributed system, such as, for example, acryptocurrency ledger or blockchain which may exist on a number ofdifferent computing devices and be reconciled in a collaborativefashion, or may be centralized. A resource tracking system may track thecontrol of resources for any number of parties. A party, such as, forexample, a source party, intermediary party, or sink party, may have aresource pool on a resource tracking system. The resource pool for aparty on a resource tracking system may include an identification of theparty and quantities of each type of resource controlled by the partyand tracked by the resource tracking system. A party may have more thanone resource type tracked by an individual resource tracking system.

A resource tracking system may track any type of resource. For example,a resource may be a computational resource such as processor time,volatile and non-volatile storage space, and network bandwidth. Therecord of ownership and quantity of a resource by the resource trackingsystem may also be the resource itself, or may be a record of ownershipof a resource that exists separately.

A resource tracking system may effect the transfer of resources betweenresource pools by modifying the quantities of resources recorded ascontrolled by the parties who control the resource pools involved in thetransfer For example, to transfer resources from a source resource poolto destination resource pool, the resource tracking system may,simultaneously or sequentially, decrease the quantity of the resourcerecorded as owned by the party which controls the source resource pooland increase the quantity of the resource recorded as owned by the partywhich controls the destination resource pool. The quantity of theresource recorded in the source resource pool may be decreased by thesame quantity that the quantity of the resource recorded in thedestination resource pool is increased. A resource tracking system maybe able to increase and decrease the quantity of resources that aretracked in resource pools on the resource tracking system, and may onlybe able to transfer resources between two parties who both have resourcepools on the resource tracking system.

The resource transfer network may be accessible to various parties,which may use the resource transfer network to transfer resources to andfrom resource pools. For example, a source party in a resource transfermay control a source resource tracking system that may have access tothe resource transfer network. The source resource tracking system mayinclude any number of resource pools, which may be controlled by thesource party, by some other party on whose behalf the source party mayact, or by an intermediary party in the resource transfer network. Thesource party may be any suitable person, group, organization, orcomputer hardware and software. An intermediary party in a resourcetransfer network may control resource pools which may be part of thelegs of the resource transfer network. These resource pools may belocated on any number of resource tracking systems in the resourcetransfer network. For example, an intermediary party may control aresource tracking system, along with resource pools on the resourcetracking system. Other parties, such as source parties, may also controlresource pools on the resource tracking system controlled by theintermediary party. An intermediary party may also control resourcepools on resource tracking system not controlled by the intermediaryparty. For example, a resource tracking system may include any number ofresource pools controlled by any number of intermediary parties. Eachresource pool may be a part of any number of legs for any number ofroutes for any suitable resource paths through the resource transfernetwork. A sink party in resource transfer network may control aresource pool on a sink resource tracking system. A sink resourcetracking system may also include resource pools controlled byintermediary parties.

For a source party to use a particular route on a resource path of theresource transfer network, the source party may need to control aresource pool on the same resource tracking system as an intermediaryparty that also controls a resource pool that can be used at the end ofthe first leg of the route. For example, if the route has one leg, thesource party may need to control a resource pool on the same resourcetracking system as the leg's intermediary party, which may also controla resource pool on the same resource tracking system as the sink partyfor the route. If the route has two legs, the source party may need tocontrol a resource pool on the same resource tracking system as theleg's intermediary party, which may also control a resource pool on thesame resource tracking system as a second intermediary party whichcontrols a resource pool on the same resource tracking system as thesink party for the route. The first leg of the route may be from theresource pool controlled by the source party to an incoming resourcepool controlled by the second intermediary party. The second leg of theroute may be from an outgoing resource pool controlled by the firstintermediary party to the resource pool of the sink party. The first andsecond leg may overlap at the resource transfer from the resource poolcontrolled by the first intermediary party to the resource poolcontrolled by the second intermediary party, which may be both the lastresource transfer of the first leg and the first resource transfer ofthe second leg, and may involve the transfer of an intermediate resourcetype.

For an intermediary party to offer a leg of a route on a resource path,the intermediary party may need to control a resource pool on the sameresource tracking system as a source party and a sink party, forexample, for a route with one leg, or a source party and anotherintermediary party or another intermediary party and a sink party, forexample, for a route with two legs. For routes with more than two legs,an intermediary party may offer a leg by controlling resource pools onthe same resource tracking system as two intermediary parties.Intermediary parties may offer any number of legs in a resource transfernetwork. Any leg offered by an intermediary party may be part of anynumber of routes on any number of resource paths. For example, a legoffered by an intermediary party between resource pools of theintermediary party and a resource pool of a sink party. Every leg may beassociated with its resource pool on a resource tracking system that isnot the source or sink resource tracking system. For example, a legoffered by an intermediary party with an incoming resource pool on asource resource tracking system and outgoing resource pool that is noton the sink resource tracking system may be associated with its outgoingresource pool. Similarly, a leg offered by an intermediary party with anincoming resource pool that is not on a source resource tracking systemand an outgoing resource pool that is on a sink resource tracking systemmay be associated with its incoming resource pool.

A party, such as a source party, may select a route to use for aspecific resource path through a resource transfer network based on thecosts of the legs of the route. Available legs in the resource transfernetwork and their costs may be advertised, such that the source party,for example, through the resource tracking system, may be able todetermine and evaluate the costs of different routes, using differentlegs, for the various resource paths of the resource transfer network.The volume of resources that may be transferred using the leg may alsobe advertised, as different legs with the same starting resource typeand ending resource type may be able to handle transfers of differentamounts of either resource type. The source party may select the routewith the lowest cost, based on the costs of the leg or legs of theroute, that is available to the source party and has legs that canhandle a large enough volume to transfer the quantities of the startingresource type and ending resource type that the source party wishes totransfer. The advertisement of a leg may be based on the resource poolwith which the leg is associated. For example, a leg that starts withthe starting resource type of a resource path and ends with anintermediate resource type may be associated with the outgoing resourcepool out of which the intermediate resource type will be transferred atthe end of the leg. The leg may be advertised based on the volume of theintermediate resource type that may be transferred out of the leg'soutgoing resource pool and the related volume of the starting resourcetype that will need to be transferred the leg's incoming resource poolto start the leg. A leg that starts with an intermediate resource typemay be associated with the incoming resource pool into which theintermediate resource type will be transferred at the beginning of theleg, and may be advertised based on the volume of the intermediateresource type that may need to be transferred into the leg's incomingresource pool to start of the leg, and the related volume of the endingresource type that will be transferred out of the leg's outgoingresource pool to end the leg.

A monitoring computing device may monitor a resource transfer network.The monitoring computing device may be any suitable computing device,with any suitable combination of hardware and software, for monitoringvarious aspects of a resource transfer network. The monitoring computingdevice may be associated with a resource pool in the resource transfernetwork. The resource pool associated with the monitoring computingdevice may be a repository resource pool located on a resource trackingsystem which may be, for example, an intermediate resource type trackingsystem, and may be operated by the same party as the monitoringcomputing device. The intermediate resource type tracking system mayinclude resource pools controlled by other parties, includingintermediary parties. The intermediary parties may also control resourcepools on other resource tracking systems on which source parties andsink parties control resource pools. The resource pools on theintermediate resource type tracking system may include quantities of anintermediate resource type, which may be used on routes with two legs.

The monitoring computing device may, through monitoring of the resourcetransfer network, determine the costs and volumes of the legs advertisedon the resource transfer network. The monitoring computing device maydetermine the costs and volumes of all, or of any subset of, the legsadvertised on the resource transfer network. For example, the monitoringcomputing device may determine the costs and volumes only for legs thatmay be used to form routes for selected resource paths. The legs may beadvertised in any suitable manner. For example, the legs may beadvertised actively, for example, through the sending of communicationsacross various systems in the resource transfer network, or passively,for example, through the posting of available legs to a designatedsystem, network-accessible location, or shared memory space in theresource transfer network.

The monitoring computing device may, after monitoring the resourcetransfer network for any suitable time period, and after the elapsing ofany suitable time period, transfer quantities of the intermediateresource type from the repository resource pool to other resource poolson the intermediate resource type tracking system. The transfer mayoccur at the end of a time period that may be a distribution period. Thequantity of the intermediate resource type transferred to a resourcepool from the repository resource pool may be determined in any suitablemanner. For example, the monitoring computing device may determine atotal quantity of the intermediate resource type to be transferred outof the repository resource pool at the end of a distribution period.This total quantity may be a reservoir resource quantity. The monitoringcomputing device may select any number of resource paths in the resourcetransfer network, for example, from the resource paths that weremonitored during the distribution period. For each selected resourcepath in the resource transfer network, the monitoring computing devicemay determine which resource pools on the intermediate resource typetracking system were associated with legs that could have been used toform routes with more than one leg for the selected resource path duringthe distribution period. The monitoring computing device may thendetermine a total volume for each of these resource pools, which may bethe total volume of the intermediate resource type that could betransferred through the routes formed using the leg with which theresource pool is associated, excluding the volume of any such routeswith costs higher than some threshold, or backstop, cost. The totalvolume may be determined over a specified time period, which may be amonitoring period and may be some portion of the distribution period.The distribution period and monitoring period may be based on theelapsing of a certain amount of time, or on the occurrence of anysuitable event. The threshold, or backstop, cost may be, for example,the cost of a selected route of the resource transfer network with onlyone leg for the selected resource path. The one leg of the selectedroute may use resource pools that are not on the intermediate resourcetype tracking system.

The monitoring computing device may determine, for each resource pool,the percentage of the reservoir resource quantity that may betransferred to that resource pool. Each selected resource path may beassigned some percentage of the reservoir resource quantity. Thepercentage of the of the reservoir resource quantity that may betransferred to a resource pool may be the total volume determined forthat resource pool as a percentage of the total volume determined forall resource pools on the intermediate resource type tracking system forthe selected resource path, as a percentage of the percentage of thereservoir resource quantity assigned to the selected resource path. Thispercentage may be determined for every resource pool that is associatedwith a leg for a selected resource path, and for every selected resourcepath. The same resource pool may have percentages determined formultiple selected resource paths if the resource pool is associated witha leg that can be used to form a route for those selected resourcepaths.

After determining the percentage for resource pools on the intermediateresource type tracking system, the monitoring computing device, or othersuitable computing device associated with the repository resource pool,may cause transfers of the intermediate resource type to the resourcepools for which percentages were determined. The resource transferquantities may be based on the determined percentages and the reservoirresource quantity. For example, the quantity of resources transferred toa resource pool may be determined by multiplying that resource pool'spercentage by the reservoir resource quantity. The resource transfersmay result in the reservoir resource quantity of the intermediateresource type being transferred out of the repository resource pool anddistributed across other resource pools on the intermediate resourcetype tracking system.

The reservoir resource quantity may be determined in any suitablemanner. For example, before the start of a first distribution period,the reservoir resource quantity may be determined based on resourcetransfers that use the selected resource paths through the resourcetransfer network over a time period of the same length as a distributionperiod. For each selected resource path, the monitoring computing devicemay monitor resource transfers that use any route across the resourcepath. The total quantity of the front resource type that is transferredin at the start of the first half of the selected resource path may bereduced by the total quantity of the front resource type that istransferred out at the end of the second half of the selected resourcepath, and if the result is less than zero, the absolute value of theresult may be the net transfer amount for the front resource type.Otherwise, if the result is zero or greater, the net transfer amount maybe zero. The total quantity of the back resource type transferred in atthe start of the second half of the selected resource path may bereduced by the total quantity of the back resource type that istransferred out at the end of the first half of the selected resourcepath, and if the result is less than zero, the absolute value of theresult may be the net transfer amount for the net transfer amount forthe back resource type. Otherwise, if the result is zero or greater, thenet transfer amount may be zero. The net transfer amounts for the frontand back resource types may each be converted, using any suitableconversion factor, to an amount of the intermediate resource type,resulting in a net intermediate resource type amount. The netintermediate resource type amounts may be summed together across everyselected resource path, resulting in the reservoir resource quantitythat will be distributed at the end of the first distribution period.

For subsequent distribution periods, the reservoir resource quantity maybe adjusted. For example, the monitoring computing device may determinethat a resource transfer in the resource transfer network used a routewith a cost higher than the threshold, or backstop, cost. This mayindicate that the reservoir resource quantity may need to be increasedfor the next distribution period. The increase may be based on, forexample, the percentage by which the current total volume of all legsavailable for the resource path where a resource transfer used a routewith a higher cost than the backstop cost exceeds the net intermediateresource type amount for the resource path from the previousdistribution period. The current total volume for the resource path maybe the total volume available through all resource pools on theintermediate resource type tracking system that are associated with aleg that can be used to form a route for the resource path added to thetotal volume available through any other resource pool in the resourcetransfer network which may be part of a one-leg route for the resourcepath. The volume of a route may only be added to the total volume forthe resource path if the route costs less than the backstop cost. Thetotal volume through resource pools that are not on the intermediateresource type tracking system may be in amounts of a resource type otherthan the intermediate resource type. The amounts may be converted to theintermediate resource type using any suitable conversion factor, inorder to allow for addition.

The monitoring computing device may determine that, for some of theselected resource paths, there are legs associated with resource poolson the intermediate resource type tracking system which do not get usedas part of a route for any resource transfer that takes place during thedistribution period. This may indicate that the reservoir resourcequantity may need to be decreased for the next distribution period. Thedecrease may be based on, for example, the percentage by which the netintermediate resource type amount for the resource path from theprevious distribution period exceeds the current total volume of alllegs available for the resource path that can be used to form routeswith a cost less than the backstop cost. The current total volume forthe resource path may be the total volume available through all resourcepools on the intermediate resource type tracking system that are part ofa leg that can be used to form a route for the resource path added tothe total volume available through any other resource pool in theresource transfer network which may be part of one leg route for theresource path. The volume of a route may only be added to the totalvolume for the resource path if the route costs less than the backstopcost. The total volume through resource pools that are not on theintermediate resource type tracking system may be in amounts of aresource type other than the intermediate resource type. The amounts maybe converted to the intermediate resource type using any suitableconversion factor, in order to allow for addition.

FIG. 1 shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter. Amonitoring computing device 100 may include a resource path monitor 110,a resource path evaluator 120, and a resource distributor 140. Themonitoring computing device 100 may be any suitable computing device,such as, for example, a computer 20 as described in FIG. 13, orcomponent thereof, for implementing the resource path monitor 110, theresource path evaluator 120, and the resource distributor 140. Themonitoring computing device 100 may be a single computing device, or mayinclude multiple connected computing devices, and may be, for example, alaptop, a desktop, an individual server, a server farm, or a distributedserver system, or may be a virtual computing device or system. Themonitoring computing device 100 may be part of a computing system andnetwork infrastructure, or may be otherwise connected to the computingsystem and network infrastructure. The resource path monitor 110 may beany suitable combination of hardware and software on the monitoringcomputing device 100 for monitoring various aspects of resource paths ina resource transfer network, including resource transfers occurringthrough the resource paths of a resource transfer network and routes andlegs available for the resource paths in the resource transfer network.The resource path evaluator 120 may be any suitable combination ofhardware and software on the monitoring computing device 100 forevaluating resource paths available in a resource transfer network basedon aspects of the resource paths determined by the resource pathmonitor. The resource distributor 130 may be any suitable combination ofhardware and software on the monitoring computing device 100 fordetermining and effecting a distribution of resources to resource poolson a resource tracking system in the resource transfer network, forexample, based on the evaluation of resource paths by the resource pathevaluator 120.

The resource path monitor 110 may be any suitable combination ofhardware and software on the monitoring computing device 100 formonitoring various aspects of resource paths in a resource transfernetwork, including resource transfers occurring through the resourcepaths of a resource transfer network and routes and legs available forthe resource paths in the resource transfer network. The resource pathmonitor 110 may monitor any suitable resource transfer network, with anysuitable number of resource tracking systems. The resource path monitor110 may be able to determine, based on monitoring of a resource transfernetwork, the resource paths that are available on the resource transfernetwork, the legs and routes which may be part of each availableresource path, and the resource tracking systems and resource poolswhich are parts of the available legs. The resource path monitor 110 maybe able to determine the advertised costs and volumes of the availablelegs for the resource transfer network. The resource path monitor 110may be able to monitor the resource transfers that take place in aresource transfer network, including the legs, with costs, andassociated resource pools used by a resource transfer, and the volume ofresources transferred by a resource transfer. The resource path monitor110 may monitor the resource transfer network using, for example, aconnection between the monitoring computing device 100 and a public orprivate communications network on which computing devices for theresource transfer network communicate. The resource path monitor 110 maymonitor the resource transfer network through active monitoring of theactivity of the computing devices in the resource transfer network, orthrough passive monitoring, for example, being sent reports of activityof the computing devices in the resource transfer network by thecomputing devices, or by other monitoring computing devices.

The resource path evaluator 120 may be any suitable combination ofhardware and software on the monitoring computing device 100 forevaluating resource paths available in a resource transfer network basedon aspects of the resource paths determined by the resource pathmonitor. The resource path evaluator 120 may be able to determine, forexample, the total quantity of resources that could have beentransferred through a resource pool that is part of a leg that can forma route for a resource path monitored by the resource path monitor 110,based on the advertised volumes as determined by the resource pathmonitor 110. The resource path evaluator 120 may be able to compare thecosts of routes on a resource path. This may allow the resource pathevaluator 120 to determine the total quantity of an intermediateresource type that could be transferred through a particular resourcepool as part of routes that costs less than some threshold, or backstop,cost for routes for a particular resource path. The resource pathevaluator 120 may be able to determine the net transfer amounts forfront and back resource types for a resource path. The resource pathevaluator 120 may perform evaluations based on data gathered by theresource path monitor 110 over any suitable period of time, such as, forexample, the distribution period, the monitoring period, or any othersuitable period of time.

The resource distributor 130 may be any suitable combination of hardwareand software on the monitoring computing device 100 for determining andeffecting a distribution of resources to resource pools on a resourcetracking system in the resource transfer network, for example, based onthe evaluation of resource paths by the resource path evaluator 120. Theresource distributor may 130 may, for example, be able to use totalquantities and net transfer amounts determined by the resource theresource path evaluator 120 to determine a reservoir resource quantityfor an intermediate resource type, and to determine the distribution ofthe reservoir resource quantity of the intermediate resource type toresource pools in a resource transfer network. The resource distributor130 may effect the distribution of the reservoir resource quantity ofthe intermediate resource type by, for example, transmitting appropriateinstructions to a resource tracking system. The instructions mayindicate the quantities of the intermediate resource type to betransferred from a resource pool that may be controlled by the sameparty that controls the monitoring computing device 100 to resourcepools controlled by various other parties. The resource distributor 130may effect the distribution of the intermediate resource type at anysuitable time, such as, for example, at the end of a distributionperiod.

FIG. 2 shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter. Aresource tracking computing device 200 may include a resource manager210 and a storage 240. The resource tracking computing device 200 may beany suitable computing device, such as, for example, a computer 20 asdescribed in FIG. 13, or component thereof, for implementing theresource manager 210 and the storage 240. The resource trackingcomputing device 200 may be a single computing device, or may includemultiple connected computing devices, and may be, for example, a laptop,a desktop, an individual server, a server farm, or a distributed serversystem, or may be a virtual computing device or system. The resourcetracking computing device 200 may be part of a computing system andnetwork infrastructure, or may be otherwise connected to the computingsystem and network infrastructure. The resource manager 210 may be anysuitable combination of hardware and software on the resource trackingcomputing device 200 for managing resources belonging to various partiesand tracked by the resource tracking computing device 200. The resourcesmay be tracked in resource pools, such as, for example, the resourcepools 242, 244, 246, and 248 in the storage 240. The storage 240 maystore the resource pools, such as the resource pools 242,244, 246, and248, for the various parties with resource tracked by the resourcetracking computing device 200. The resource pools 242, 244, 246, and 248may be records of resources controlled by parties and tracked by theresource tracking computing device 200, including the types andquantities of the resources, and an identification of the party thatcontrols the resources recorded by the resource pool. The resourcetracking computing device 200 may be, for example, an intermediateresource type tracking system, which may or may not be affiliated withor belong to a particular person or organization, or may be a componentof a server system.

The resource manager 210 may be any suitable combination of hardware andsoftware on the resource tracking computing device 200 for managingresources tracked by the resource tracking computing device 200. Theresource manager 210 may be able to receive instructions to performresource transfers between resource pools, such as the resource pools242, 244, 246, and 248, on the resource tracking computing device 200.The instructions, which may be execute instructions for resourcetransfers, may indicate that resources tracked by the resource trackingcomputing device 200 are to be transferred from one resource pool on theresource tracking computing device 200 to another resource pool on theresource tracking computing device 200. The resource manager 210 may beable to receive an execute instruction and execute the transfer ofresource. The resource manager 210 may be able to transfer resourcesbetween resource pools, such as the resource pool 242 and the resourcepool 244, by decrementing the quantity of the resources in one resourcepool and incrementing the quantity of the resources in the otherresource pool by the same quantity.

FIG. 3 shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.The resource pool 242 on the resource tracking computing device 200 mayinclude a resource owner identifier 310, and resource records 320 and330. The resource owner identifier 310 may be any suitableidentification of the party that controls the resources recorded in theresource pool 242. For example, the resource owner identifier may be aname of a person, organization, or user or process on a server system,an arbitrary name, a username and password combination, a passphrase orpasscode, a unique number, or a cryptographic public key. The resourcerecords 320 and 330 may include resource types 322 and 332, and resourcequantities 324 and 334. The resource types 322 and 332 may indicate thetype of resource that is recorded in the resource records 320 and 330.The resource types 322 and 332 may be any suitable resource, such as,for example, currency, cryptocurrency, commodities, financialinstruments, or computational resources. The resource quantities 322 and324 may indicate the quantity of the resource types 322 and 332controlled by the party identified by the resource owner identifier 310and tracked in the resource pool 242. The resource quantities 322 and324 may be stored in, for example, registers or memory cells on theresource tracking computing device 200.

The resource tracking computing device 200 may track resources in anysuitable manner. For example, the resource tracking computing device 200may pool resources by type, with each resource pool, such as theresource pool 242, tracking a particular resource type, such as theresource type 322. The resource pool 242 may then include the resourcequantity 324 of the resource type 322 controlled by each party thatcontrols any amount of the resource type 322, using resource owneridentifiers such as the resource owner identifier 310.

FIG. 4 shows an example arrangement suitable for a resource distributionsystem according to an implementation of the disclosed subject matter. Aresource path in a resource transfer network may include routes that maystart at any of a number of source resource tracking computing devicesand end at any of a number of sink resource tracking computing devices.The resource transfer network may include routes with one leg for theresource path. Routes with one leg for a resource path may allow for aresource transfer starting at a source resource tracking computingdevice, such as the source resource tracking computing device 410 andending at a sink resource tracking computing device, such as, forexample, any of the sink resource tracking computing devices 420, 430,440, and 450. The routes with one leg may go through resource trackingcomputing devices such as, for example, resource tracking computingdevices 460, 470, 480, and 490. Different routes with one leg on thesame resource path may go through different ones of the resourcetracking computing devices 460, 470, 480, and 490, and the routesavailable for a particular resource transfer may depend on the desiredsink resource tracking computing device. For example, if the sinkresource tracking computing device 420 is the sink resource trackingcomputing device for a resource transfer, a route with one leg throughthe resource tracking computing device 460 may be available, but noother routes may be available. If the sink resource tracking computingdevice 440 is the sink resource tracking computing device for theresource transfer, routes with one leg through the resource trackingcomputing devices 470, 480, and 490 may be available, but no routethrough the resource tracking computing device 460 may available.

FIG. 5A shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter. Aroute with one leg may be used to execute a resource transfer. Thesource resource tracking computing device 410 may send an executeinstruction to the resource tracking computing device 460. The resourcetracking computing device 460 may include the resource pool 510, whichmay be controlled by a party indicated by the resource owner identifier512. The party indicated by the resource owner identifier 512 maycontrol the source resource tracking computing device 410. On receivingthe execute instruction, the resource manager 502 may decrement resourcequantity 519, which may lessen the quantity of resource type 517recorded in resource record 515 as being in the resource pool 510. Theresource type 517 may be, for example, the front resource type of theresource path for the resource transfer, and the starting resource typefor one leg of the route being used. The resource manager 502 mayincrement resource quantity 529, which may increase the quantity ofresource type 517 recorded in resource record 525 as being in resourcepool 520. The resource pool 520 may be controlled by a party indicatedby the resource owner identifier 522, which may be a different partythan the party indicated by the resource owner identifier 512. Theresource pool 520 may be the incoming resource pool for the leg. Theamounts by which the resource quantity 519 is decremented and theresource quantity 529 is incremented may be equal, and may be specified,for example, by the execution instruction, or by a separately receivedmessage or instruction. In some implementations, the party indicated bythe resource owner identifier 522 may control the resource trackingcomputing device 460.

FIG. 5B shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.The resource tracking computing device 460 may send an executeinstruction to the sink resource tracking computing device 420. In someimplementations, the execute instruction may be sent by anothercomputing device that may be controlled by the party indicated by theresource owner identifier 522. The sink resource tracking computingdevice 420 may include the resource pool 530, which may be controlled bythe party indicated by the resource owner identifier 522, and may be theoutgoing resource pool for the leg. On receiving the executeinstruction, the resource manager 503 may decrement resource quantity539, which may lessen the quantity of resource type 537 recorded inresource record 535 as being in the resource pool 530. The resource type537 may be the back resource type of the resource path for the resourcetransfer, and the ending resource type for one leg of the route beingused. The resource manager 503 may increment resource quantity 549,which may increase the quantity of resource type 537 recorded inresource record 545 as being in resource pool 540. The resource pool 540may be controlled by a party indicated by the resource owner identifier542, which may be a different party than the parties indicated by theresource owner identifier 512 and 522, and may be a sink party for theresource transfer. The amounts by which the resource quantity 539 isdecremented and the resource quantity 549 is incremented may be equal,and may be specified, for example, by the execution instruction, or by aseparately received message or instruction. This may complete the oneleg of the route used for the resource path, completing the resourcetransfer. The resource transfer may include a cost. The cost may be thedifference between the quantity decremented from the resource quantity519, and the quantity that would have been decremented from the resourcequantity 519 if the resource pool 540 included a resource record for theresource type 517, allowing for the completion of a resource transferwithout the resource pools 520 and 530.

FIG. 6 shows an example arrangement suitable for a resource distributionsystem according to an implementation of the disclosed subject matter. Aresource transfer network may include routes with two legs for aresource path. Routes with two legs for a resource path may allow for aresource transfer starting at a source resource tracking computingdevice, such as the source resource tracking computing device 510 andending at a sink resource tracking computing device, such as, forexample, any of the sink resource tracking computing devices 520, 530,540, and 550. The routes with two legs may go through a resourcetracking computing device such as, for example, resource trackingcomputing device 200. The resource tracking computing device 200 maymake routes with two legs available between the source resource trackingcomputing device 510 and any of the sink resource tracking computingdevices 520, 530, 540, and 550. The resource tracking computing device200 may make such routes available for any number of resource paths,such that it may be possible to complete any resource transfer possiblein the resource transfer network using a route with two legs through theresource tracking computing device 200.

FIG. 7A shows an example arrangement suitable for a resourcedistribution system according to an implementation of the disclosedsubject matter. A route with two legs may be used to execute a resourcetransfer. The source resource tracking computing device 410 may includethe resource pool 700, which may be controlled by the party indicated bythe resource owner identifier 512. The party indicated by the resourceowner identifier 512 may control the source resource tracking computingdevice 410. The resource manager 791, on instruction from sourceresource tracking computing device 410, may decrement resource quantity519, which may lessen the quantity of resource type 517 recorded inresource record 705 as being in the resource pool 700. The resource type517 may be the front resource type of the resource path for the resourcetransfer, and the starting resource type for first leg of the routebeing used. The resource manager 791 may increment resource quantity719, which may increase the quantity of resource type 517 recorded inresource record 715 as being in resource pool 710, which may be theincoming resource pool for the first leg. The resource pool 710 may becontrolled by a party indicated by the resource owner identifier 712,which may be a different party than the party indicated by the resourceowner identifier 512. The amounts by which the resource quantity 519 isdecremented and the resource quantity 719 is incremented may be equal,and may be specified, for example, by the execution instruction, or by aseparately received message or instruction.

An execute instruction may be sent to the resource tracking computingdevice 200. The execute instruction may be sent by, for example, thesource resource tracking computing device 410, or by another computingdevice, such as, for example, a computing device controlled by the partindicated by the resource owner identifier 712. The resource trackingcomputing device 200 may include the resource pool 720, which may becontrolled by a party indicated by the resource owner identifier 712 andmay be the outgoing resource pool for the first leg. On receiving theexecute instruction, the resource manager 210 may decrement resourcequantity 729, which may lessen the quantity of resource type 717recorded in resource record 725 as being in the resource pool 720. Theresource type 717 may be the intermediate resource type, the endingresource type for first leg of the route being used, and the startingresource type for the second leg of the route being used. The resourcemanager 210 may increment resource quantity 739, which may increase thequantity of resource type 717 recorded in resource record 735 as beingin resource pool 730, which may be the incoming resource pool for thesecond leg. The resource pool 730 may be controlled by a party indicatedby the resource owner identifier 732, which may be a different partythan the parties indicated by the resource owner identifier 512 and 712.The amounts by which the resource quantity 729 is decremented and theresource quantity 739 is incremented may be equal, and may be specified,for example, by the execution instruction, or by a separately receivedmessage or instruction. This may complete the first leg of the routeused for the resource path, and start the second leg of the route.

FIG. 7B shows an example arrangement suitable for a resourcedistribution system according to an implementation of the disclosedsubject matter. The resource tracking computing device 200 may send anexecute instruction to the sink resource tracking computing device 420.In some implementations, the execute instruction may be sent by anothercomputing device that may be controlled by the party indicated by theresource owner identifier 732. The sink resource tracking computingdevice 420 may include the resource pool 740, which may be controlled bythe party indicated by the resource owner identifier 732 and may be theoutgoing resource pool for the second leg. On receiving the executeinstruction, the resource manager 503 may decrement resource quantity749, which may lessen the quantity of resource type 537 recorded inresource record 745 as being in the resource pool 740. The resource type537 may be the back resource type of the resource path for the resourcetransfer, and the ending resource type for second leg of the route beingused. The resource manager 503 may increment resource quantity 549,which may increase the quantity of resource type 537 recorded inresource record 545 as being in resource pool 540. The resource pool 540may be controlled by a party indicated by the resource owner identifier542, which may be a different party than the parties indicated by theresource owner identifier 512, 712, and 732, and may be a sink party forthe resource transfer. The amounts by which the resource quantity 749 isdecremented and the resource quantity 549 is incremented may be equal,and may be specified, for example, by the execution instruction, or by aseparately received message or instruction. This may complete the secondleg of the route used for the resource path, completing the resourcetransfer. The resource transfer may include a cost. The cost may be thedifference between the quantity decremented from the resource quantity519, and the quantity that would have been decremented from the resourcequantity 519 if the resource pool 540 included a resource record for theresource type 517, allowing for the completion of a resource transferwithout the resource pools 710, 720, 730, and 740. Each leg of the routemay be responsible for any portion of the cost of the resource transfer.

FIG. 7C shows an example arrangement suitable for a resourcedistribution system according to an implementation of the disclosedsubject matter. In some implementations, the sink resource trackingcomputing device 420 may include a resource pool 750, which may becontrolled by the party indicated by the resource owner identifier 712.After the execute instruction is sent to the resource tracking computingdevice 200, the resource manager 210 may decrement the resource quantity729, which may lessen the quantity of the resource type 717 recorded inthe resource record 725 as being in the resource pool 720, and mayincrement resource quantity 799, which may increase the quantity ofresource type 717 recorded in resource record 795 as being in resourcepool 790. The resource pool 790 may be controlled by a party indicatedby the resource owner identifier 792, which may be a different partythan the parties indicated by the resource owner identifier 512 and 712,and may be the party that controls the resource tracking computing 200.The amounts by which the resource quantity 729 is decremented and theresource quantity 799 is incremented may be equal, and may be specified,for example, by the execution instruction, or by a separately receivedmessage or instruction. The resource manager 210 may then, after anysuitable period of time, decrement the resource quantity 799 by the samequantity by which it was incremented, and may increment the resourcequantity 729 by the same quantity by which it was decremented. This maycomplete the first leg of the route used for the resource path, andstart the second leg of the route.

The resource tracking computing device 200 may send an executeinstruction to the sink resource tracking computing device 420. Onreceiving the execute instruction, the resource manager 503 maydecrement resource quantity 759, which may lessen the quantity ofresource type 537 recorded in resource record 755 as being in theresource pool 750, which may be controlled by the party indicated by theresource owner identifier 712. The resource manager 503 may incrementresource quantity 549, which may increase the quantity of resource type537 recorded in resource record 545 as being in resource pool 540. Theresource pool 540 may be controlled by a party indicated by the resourceowner identifier 542, which may be a different party than the partiesindicated by the resource owner identifier 512, 712, and 792, and may bea sink party for the resource transfer. The amounts by which theresource quantity 759 is decremented and the resource quantity 549 isincremented may be equal, and may be specified, for example, by theexecution instruction, or by a separately received message orinstruction. This may complete the second leg of the route used for theresource path, completing the resource transfer.

FIG. 8 shows an example system suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.Route 810 may include one leg. X quantity of the resource type 617 maybe transferred out of a resource pool controlled by the party indicatedby the resource owner identifier 612 and into a resource pool controlledby the party indicated by the resource owner identifier 622. This mayoccur, for example, on a resource tracking computing device such as theresource tracking computing device 460. Y quantity of the resource type637 may be transferred out of a resource pool controlled by the partyindicated by the resource owner identifier 622 and into a resource poolcontrolled by the party indicated by the resource owner identifier 642,completing the resource transfer. This may occur, for example, on aresource tracking computing device such as the sink resource trackingcomputing device 520.

Route 820 may include two legs. X quantity of the resource type 617 maybe transferred out of a resource pool controlled by the party indicatedby the resource owner identifier 612 and into a resource pool controlledby the party indicated by the resource owner identifier 622. This mayoccur, for example, on a resource tracking computing device such as thesource resource tracking computing device 410. Z quantity of theresource type 717 may be transferred out of a resource pool controlledby the party indicated by the resource owner identifier 712 and into aresource pool controlled by the party indicated by the resource owneridentifier 732, completing the first leg of the route and starting thesecond leg of the route. This may occur, for example, on a resourcetracking computing device such as the resource tracking computing device200. Y quantity of the resource type 637 may be transferred out of aresource pool controlled by the party indicated by the resource owneridentifier 732 and into a resource pool controlled by the partyindicated by the resource owner identifier 642, completing the secondleg of the route, and completing the resource transfer. This may occur,for example, on a resource tracking computing device such as the sinkresource tracking computing device 520.

Route 830 may include two legs. X quantity of the resource type 617 maybe transferred out of a resource pool controlled by the party indicatedby the resource owner identifier 612 and into a resource pool controlledby the party indicated by the resource owner identifier 622. This mayoccur, for example, on a resource tracking computing device such as thesource resource tracking computing device 410. Z quantity of theresource type 717 may be transferred out of a resource pool controlledby the party indicated by the resource owner identifier 712 and into aresource pool controlled by the party indicated by the resource owneridentifier 790. Z quantity of the resource type 717 may then betransferred out of the resource pool controlled by the part indicated bythe resource owner identifier 790 back into the resource pool controlledby party indicated by the resource owner identifier 712, completing thefirst leg of the route and starting the second leg of the route. Thismay occur, for example, on a resource tracking computing device such asthe resource tracking computing device 200. Y quantity of the resourcetype 637 may be transferred out of a resource pool controlled by theparty indicated by the resource owner identifier 712 and into a resourcepool controlled by the party indicated by the resource owner identifier642, completing the second leg of the route, and completing the resourcetransfer. This may occur, for example, on a resource tracking computingdevice such as the sink resource tracking computing device 520.

FIG. 9 shows an example arrangement suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.The activity of various resource tracking computing devices in aresource transfer network may be monitored by the monitoring computingdevice 100. For example, the monitoring computing device 100 may monitorany resource tracking computing device, such as the resource trackingcomputing devices 200, 560, 570, 580, and 590, which are not a source orsink resource tracking computing device in the resource transfernetwork. The resource path monitor 110 may monitor resource pathactivity for selected resource paths in the resource transfer network.The monitored activity may be, for example, the advertised volumes andcosts of the legs made available by resource pools on the variousmonitored resource tracking computing devices that may be used to formroutes for the resource paths being monitored, or the actual transferredamounts of resources across selected resource paths. For example, theadvertised volumes and costs of legs may be broadcast or otherwise madeavailable publicly, for example being stored in a shared memory space ornetwork accessible memory space, by the resource tracking computingdevices 200, 560, 570, 580, and 590.

The resource path monitor 110 may monitor activity of the resourcetransfer network over any suitable period of time, such as, for example,over a monitoring period. The monitoring period may be any suitableamount of time that may be less than or equal to a distribution period.At the end of a monitoring period, the resource path activity asdetermined by the resource path monitor 110 may be sent to the resourcepath evaluator 120. The resource path evaluator 120 may evaluate theresource path activity of the selected resource paths that weremonitored by the resource path monitor 110. The resource path evaluator120 may, for example, determine the total volume of an intermediateresource type, such as the resource type 717, that could have beentransferred through each of the resource pools on the resource trackingcomputing device 200 associated with a leg used to form a route for oneof the selected resource paths, excluding the volume of any routes witha cost higher than a threshold, or backstop, cost for that resourcepath. The threshold or backstop cost for a resource path may be the costof a route for the resource path that uses only one leg, such as theroute 810. The resource path evaluator 120 may be able to determine nettransfer amounts for the front and back resource types of the resourcepaths in the resource transfer network. The resource path evaluator 120may use the actual amount of transferred resources across a selectedresource path, as determined by the resource path monitor 110, todetermine net transfer amounts. The resource path evaluator 120 may alsodetermine, for example, when a route for a resource path in the resourcetransfer network with a higher cost than the threshold, or backstop,cost for that resource path was used in a resource transfer, or when arelegs associated with resource pools on the resource tracking computingdevice 200 do not get used as part of a route for any resource transferthat takes place during the distribution period.

The resource distributor 130 may receive resource path evaluations fromthe resource path evaluator 120, including, for example, any suitablecombination of total volumes of the resource type 717 that could havebeen transferred through each of the resource pools on the resourcetracking computing device 200 associated with a leg used to form a routefor one of the selected resource paths, excluding the volume of any suchroutes with costs higher than some threshold, or backstop, cost, and nettransfer amounts for the selected resource paths. The resourcedistributor 130 may use the net transfer amounts to determine areservoir resource quantity for the resource transfer network, forexample, before the end of the first distribution period. The resourcedistributor 130 may assign a percentage of the reservoir resourcequantity to each of the selected resource paths in any suitable manner.The resource distributor 130 may use the total volumes of the resourcetype 717 that could have been transferred through each of the resourcepools on the resource tracking computing device 200 to determine theportion of the reservoir resource quantity that may distributed to eachof these resource pools at the end of each distribution period. Theresource distributor 130 may effect the distribution of the portions ofthe reservoir resource quantity to the resource pools on the resourcetracking computing device 200, for example, sending distributioninstructions, which may include execute instructions, to the resourcetracking computing device 200. The resource distributor may alsodetermine adjustments to the reservoir resource quantity based onwhether the resource path evaluator 120 determined that a route for aresource path in the resource transfer network with a higher cost thanthe threshold, or backstop, cost for that resource path was used in aresource transfer, or that there are legs associated with resource poolson the resource tracking computing device 200 that did not get used aspart of a route for any resource transfer that took place during thedistribution period.

FIG. 10 shows an example arrangement suitable for a resourcedistribution system according to an implementation of the disclosedsubject matter. The distribution instructions from the resourcedistributor 130 may be sent to the resource manager 210 of the resourcetracking computing device 200. The distribution instructions may includeany suitable number of execute instructions for transfers from theresource pool 790 to other resource pools, such as the resource pool730, on the resource tracking computing device 200. The resource pool790 may be the repository resource pool. The resource pool 790 mayinclude the resource record 1020, which may include a record of theresource quantity 1024 for the resource type 717, from which thereservoir resource quantity may be taken. For example, the distributioninstructions may indicate that some portion of the reservoir resourcequantity should be transferred to the resource pool 730. The resourcequantity 1024 may be decremented, and the resource quantity 759, by theappropriate amount. The resource quantity 1024 may be furtherdecremented to transfer other portions of the reservoir resourcequantity to other resource pools on the resource tracking computingdevice 200 in accordance with the distribution instructions.

FIG. 11 shows an example arrangement suitable for a resourcedistribution system according to an implementation of the disclosedsubject matter. A first half of a resource path 1105 in a resourcetransfer network may allow for a resource transfer that starts with theresource type 1110 and ends with the resource type 1150. Routes with twolegs may go through the resource tracking computing device 200, and anyof the resource pools 242, 244, and 246. For example, leg 1121 may startwith the resource type 1110 being transferred out of a resource poolcontrolled by a source party and end with an intermediate resource type,such as the resource type 717, being transferred out of the resourcepool 242 and into either the resource pool 244 or 246. The leg 1121 maybe associated with the resource pool 242. Leg 1131 may start with theintermediate resource type being transferred into the resource pool 246,and end with the resource type 1150 being transferred to a resource poolcontrolled by a sink party. The leg 1131 may be associated with theresource pool 246. Leg 1122 may start with the resource type 1110 beingtransferred out of a resource pool controlled by a source party and endwith an intermediate resource type, such as the resource type 717, beingtransferred out of the resource pool 244. The leg 1122 may be associatedwith the resource pool 244. Leg 1132 may start with the intermediateresource type being transferred into the resource pool 244, and end withthe resource type 1150 being transferred to a resource pool controlledby a sink party. The leg 1132 may be associated with the resource pool244. Leg 1123 may start with resource type 1110 being transferred out ofa resource pool controlled by a source party into a resource pool on theresource tracking computing device 570, and end with the resource type1150 being transferred into a resource pool controlled by a sink party.The leg 1123 may be associated with the resource pool on the resourcetracking computing device 570. Leg 1124 may start with resource type1110 being transferred out of a resource pool controlled by a sourceparty into a resource pool on the resource tracking computing device560, and end with the resource type 1150 being transferred into aresource pool controlled by a sink party. The leg 1124 may be associatedwith the resource pool on the resource tracking computing device 560.The leg 1121, 1122, 1123, 1124, 1131, and 1132 may be used to formroutes for the first half of the resource path 1105. For example, theleg 1121 may form a route with the leg 1131 or the leg 1132. The leg1122 may form a route with the leg 1131 or the leg 1132. The leg 1123may be a one-leg route, and the leg 1124 may be one-leg route.

Each of the legs 1121, 1122, 1123, 1124, and 1125 may have its volumeand cost advertised. The resource pools 242, 244, and 246, and theresource pools on the resource tracking computing devices 560 and 570,may each be associated with additional legs that may be used to formroutes for the resource path 1105. The additional legs may have theirown volumes and costs. For example the leg 1121 may be advertised with afirst volume of the intermediate resource that may be transferred out ofthe resource pool 242, along with an associated first cost. The resourcepool 242 may be associated with another leg, which may also begin withthe resource type 1110 and end with the intermediate resource type,which may be advertised with a second volume and a second cost, whichmay differ from the first volume and the first cost. The resource pools242, 244, and 246, and the resource pools on the resource trackingcomputing devices 560 and 570, may also be associated with legs that maybe used to form routes for the second half of the resource path 1105,which may begin with the resource type 1150 and end with the resourcetype 1110. Portions of the reservoir resource quantity may bedistributed to the resource pools 242, 244, and 246, based, for example,on the advertised volumes and costs of the legs 1121, 1122, 1123, and1124, and any other advertised legs associated with the resource pools242, 244, and 246 that be used to form routes for the resource path1105.

FIG. 12 shows an example procedure suitable for a resource distributionsystem according to an implementation of the disclosed subject matter.At 1200, selected resource paths may be monitored. For example, themonitoring computing device 100 may monitor selected resource paths in aresource transfer network. The monitoring computing device 100 maymonitor activity of the selected resource paths, including quantities offront and back resources transferred into and out of resource poolsduring resource transfers across the selected resource paths. Themonitoring computing device 100 may monitor the selected resource pathsfor any suitable period of time.

At 1202, a reservoir resource quantity may be determined. For example,the monitoring computing device 100 may determine a reservoir resourcequantity in any suitable manner based on the monitoring of the activityof the selected resource paths in the resource transfer network. Themonitoring computing device 100 may, for example, determine net transferamounts for each front and back resource type for each selected resourcepath, convert the net transfer amounts for each front and back resourcetype into an amount of an intermediate resource type, and sum theconverted amounts to determine the reservoir resource quantity.

At 1204, selected resource paths may be monitored. For example, themonitoring computing device 100 may monitor the same selected resourcepaths in the resource transfer network that were monitored to determinethe reservoir resource quantity. This may start a monitoring period,which may coincide with the start of a distribution period, or may takeplace any suitable amount of time after a distribution period hasstarted. The monitoring computing device 100 may monitor the variousadvertised legs that may be used to form routes for the selectedresource paths, including the costs and volumes of legs associated withresource pools on an intermediate resource type tracking system, such asthe resource tracking computing device 200, and resource transfers thattake place using legs associated with these resource pools. Themonitoring computing device 100 may also monitor activity on routes forthe selected resource paths that use only one leg, for example, goingthrough resource pools on resource tracking computing devices other thanresource tracking computing device 200, and the costs of any such routesused for a resource transfer during the monitoring period.

At 1206, whether the monitoring period has ended may be determined. Forexample, if an appropriate amount of time has elapsed since the start ofthe monitoring period, the monitoring period may be ended, and flow mayproceed to 1208. Otherwise flow may proceed back to 1204, wheremonitoring of the selected resource paths may continue.

At 1208, whether the distribution period has ended may be determined.For example, if an appropriate amount of time has elapsed since thestart of the distribution period, the distribution period may be ended,and flow may proceed to 1210. Otherwise, flow may proceed to 1208 untilthe distribution period ends.

At 1210, a resource distribution may be determined. For example, themonitoring computing device 100 may determine the portions of thereservoir resource quantity to distribute from a repository resourcepool to other resource pools on the resource tracking computing device200. The portion distributed to a resource pool on the resource trackingcomputing device 200 may be based on, for example, the selected resourcepaths for which legs associated with the resource pool could be used toform routes. For each selected resource path, the volumes of theadvertised leg associated with the resource pool that could be used toform a route with a cost below a threshold cost may be totaled, and thetotal may be divided the total volume of the legs associated with allresource pools on the resource tracking computing device 200 that couldbe used to form a route for the same selected resource path. Thispercentage may then be multiplied by the portion of the reservoirresource quantity assigned to the selected resource path to determinethe amount of the reservoir resource quantity that will be transferredto the resource pool based on the resource pool's associated legs forthe selected resource path. This may be repeated for each resource poolon the resource tracking computing device 200, and each selectedresource path, to determine distribution instructions. A resource poolassociated with legs that could be used to form below-threshold costroutes for multiple resource paths may receive some portion of thereservoir resource quantity based on each of the multiple resourcepaths. For example, a resource pool may be associated with one leg thatmay be used to form routes for two selected resource paths, or may beassociated with two legs, each of which may be used to form a route fora different resource path.

At 1214, distribution instructions may be sent. For example, themonitoring computing device 100 may send distribution instructions tothe resource tracking computing device 200. The distributioninstructions may include execute instructions, which may cause theresource manager 210 to decrement the quantity of an intermediateresource type recorded by a repository resource pool, for example, theresource pool 790, by some quantity, which may be equal to the reservoirresource quantity, and to increment the quantity of the intermediateresource type recorded by various resource pools on the resourcetracking computing device 200, such as the resource pools 242, 244, 246,248, 720, and 730, by their determined portion of the reservoir resourcequantity. This may effect distribution of the reservoir resourcequantity from the repository resource pool to the resource pools whichwere associated with legs that could be sued to form routes with belowthreshold costs for the selected resource paths.

At 1216, the reservoir resource quantity may be adjusted. For example,the monitoring computing device 100 may determine that, during themonitoring period, a resource transfer occurred on one of the selectedresource paths using a route with one leg and having a cost higher thana threshold, or backstop cost, for that resource path. The monitoringcomputing device 100 may increase the reservoir resource quantity, forexample, based on the percentage by which the current total volume forall legs available for the selected resource path exceeds the netintermediate resource type amount for the resource path from theprevious distribution period. The monitoring computing device 100 maydetermine that, during the monitoring period, a resource pool on theresource tracking computing device 200 was associated with a leg thatwas not used to form a route for any resource transfer. The monitoringcomputing device 100 may decrease the reservoir resource quantity, forexample, based on the percentage by which the net intermediate resourcetype amount for the resource path from the previous distribution periodexceeds the current total volume of all legs in the resource path thatform routes with a cost less than the backstop cost.

Implementations of the presently disclosed subject matter may beimplemented in and used with a variety of component and networkarchitectures. FIG. 13 is an example computer 20 suitable forimplementations of the presently disclosed subject matter. The computer20 includes a bus 21 which interconnects major components of thecomputer 20, such as a central processor 24, a memory 27 (typically RAM,but which may also include ROM, flash RAM, or the like), an input/outputcontroller 28, a user display 22, such as a display screen via a displayadapter, a user input interface 26, which may include one or morecontrollers and associated user input devices such as a keyboard, mouse,and the like, and may be closely coupled to the I/O controller 28, fixedstorage 23, such as a hard drive, flash storage, Fibre Channel network,SAN device, SCSI device, and the like, and a removable media component25 operative to control and receive an optical disk, flash drive, andthe like.

The bus 21 allows data communication between the central processor 24and the memory 27, which may include read-only memory (ROM) or flashmemory (neither shown), and random access memory (RAM) (not shown), aspreviously noted. The RAM is generally the main memory into which theoperating system and application programs are loaded. The ROM or flashmemory can contain, among other code, the Basic Input-Output system(BIOS) which controls basic hardware operation such as the interactionwith peripheral components. Applications resident with the computer 20are generally stored on and accessed via a computer readable medium,such as a hard disk drive (e.g., fixed storage 23), an optical drive,floppy disk, or other storage medium 25.

The fixed storage 23 may be integral with the computer 20 or may beseparate and accessed through other interfaces. A network interface 29may provide a direct connection to a remote server via a telephone link,to the Internet via an internet service provider (ISP), or a directconnection to a remote server via a direct network link to the Internetvia a POP (point of presence) or other technique. The network interface29 may provide such connection using wireless techniques, includingdigital cellular telephone connection, Cellular Digital Packet Data(CDPD) connection, digital satellite data connection or the like. Forexample, the network interface 29 may allow the computer to communicatewith other computers via one or more local, wide-area, or othernetworks, as shown in FIG. 14.

Many other devices or components (not shown) may be connected in asimilar manner (e.g., document scanners, digital cameras and so on).Conversely, all of the components shown in FIG. 13 need not be presentto practice the present disclosure. The components can be interconnectedin different ways from that shown. The operation of a computer such asthat shown in FIG. 13 is readily known in the art and is not discussedin detail in this application. Code to implement the present disclosurecan be stored in computer-readable storage media such as one or more ofthe memory 27, fixed storage 23, removable media 25, or on a remotestorage location.

FIG. 14 shows an example network arrangement according to animplementation of the disclosed subject matter. One or more clients 10,11, such as local computers, smart phones, tablet computing devices, andthe like may connect to other devices via one or more networks 7. Thenetwork may be a local network, wide-area network, the Internet, or anyother suitable communication network or networks, and may be implementedon any suitable platform including wired and/or wireless networks. Theclients may communicate with one or more servers 13 and/or databases 15.The devices may be directly accessible by the clients 10, 11, or one ormore other devices may provide intermediary access such as where aserver 13 provides access to resources stored in a database 15. Theclients 10, 11 also may access remote platforms 17 or services providedby remote platforms 17 such as cloud computing arrangements andservices. The remote platform 17 may include one or more servers 13and/or databases 15.

More generally, various implementations of the presently disclosedsubject matter may include or be implemented in the form ofcomputer-implemented processes and apparatuses for practicing thoseprocesses. Implementations also may be implemented in the form of acomputer program product having computer program code containinginstructions implemented in non-transitory and/or tangible media, suchas floppy diskettes, CD-ROMs, hard drives, USB (universal serial bus)drives, or any other machine readable storage medium, wherein, when thecomputer program code is loaded into and executed by a computer, thecomputer becomes an apparatus for practicing implementations of thedisclosed subject matter. Implementations also may be implemented in theform of computer program code, for example, whether stored in a storagemedium, loaded into and/or executed by a computer, or transmitted oversome transmission medium, such as over electrical wiring or cabling,through fiber optics, or via electromagnetic radiation, wherein when thecomputer program code is loaded into and executed by a computer, thecomputer becomes an apparatus for practicing implementations of thedisclosed subject matter. When implemented on a general-purposemicroprocessor, the computer program code segments configure themicroprocessor to create specific logic circuits. In someconfigurations, a set of computer-readable instructions stored on acomputer-readable storage medium may be implemented by a general-purposeprocessor, which may transform the general-purpose processor or a devicecontaining the general-purpose processor into a special-purpose deviceconfigured to implement or carry out the instructions. Implementationsmay be implemented using hardware that may include a processor, such asa general purpose microprocessor and/or an Application SpecificIntegrated Circuit (ASIC) that implements all or part of the techniquesaccording to implementations of the disclosed subject matter in hardwareand/or firmware. The processor may be coupled to memory, such as RAM,ROM, flash memory, a hard disk or any other device capable of storingelectronic information. The memory may store instructions adapted to beexecuted by the processor to perform the techniques according toimplementations of the disclosed subject matter.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific implementations. However, theillustrative discussions above are not intended to be exhaustive or tolimit implementations of the disclosed subject matter to the preciseforms disclosed. Many modifications and variations are possible in viewof the above teachings. The implementations were chosen and described inorder to explain the principles of implementations of the disclosedsubject matter and their practical applications, to thereby enableothers skilled in the art to utilize those implementations as well asvarious implementations with various modifications as may be suited tothe particular use contemplated.

The invention claimed is:
 1. A computer-implemented method performed ona data processing apparatus comprising: receiving an indication of anavailable leg for a resource path, the resource path comprising a frontresource type and a back resource type, the available leg associatedwith a resource pool comprising a register indicating a quantity of anintermediate resource type, wherein the available leg can be used toform a route for half of the resource path; determining from theindication of the available leg a total quantity of an intermediateresource type transferrable either out of or into the resource poolassociated with the leg based on monitoring of the resource path over amonitoring period which occurs during a distribution period; determininga quantity of the intermediate resource type to be transferred into theresource pool associated with the leg based on the total quantity of theintermediate resource type transferrable either out of or into resourcepool associated with the leg; and generating and causing to be executed,at the end of the distribution period, instructions decrementing aregister in a repository resource pool by the determined quantity of theintermediate resource type to be transferred into the resource poolassociated with the leg and incrementing the register in the resourcepool associated with the leg by the determined quantity of theintermediate resource type to be transferred into the resource poolassociated with the leg.
 2. The method of claim 1, wherein theindication of the available leg further comprises a cost of theavailable leg.
 3. The method of claim 2, wherein a route for theresource path comprises the available leg and another leg, the routecomprising a cost that is the sum of the cost of the available leg andthe cost of the another leg.
 4. The method of claim 3, wherein the totalquantity of the intermediate resource type transferrable either out ofor into the resource pool associated with the leg when the leg is usedfor the resource path comprises the sum of the quantities of theintermediate resource type transferrable either out of or into theresource pool associated with the leg when the leg is part of a routefor half of the resource path and the cost of the route is less than athreshold cost for the half of the resource path.
 5. The method of claim4, wherein the threshold cost for the resource path comprises a cost ofa one-leg route for the half of the resource path.
 6. The method ofclaim 1, wherein the quantity of the intermediate resource type to betransferred into the resource pool associated with the leg is furtherbased on a portion of a reservoir resource quantity assigned to theresource path.
 7. A computer-implemented method performed on a dataprocessing apparatus comprising: monitoring a plurality of selectedresource paths in a resource transfer network; determining a quantity ofan intermediate resource type to transfer into each of a plurality ofresource pools in the resource transfer network, each of the pluralityof resource pools associated with at least one leg that can be part of aroute with two legs for at least one of the selected resource paths; andgenerating and causing to be executed instructions decrementing aregister in a repository resource pool by the determined quantities ofthe intermediate resource type to be transferred into the plurality ofresource pools in the resource transfer network and incrementing aregister in each of the plurality of resource pools in the resourcetransfer network by the determined quantity of the intermediate resourcetype to be transferred into that resource pool when the determinedquantity is greater than zero; wherein the determined quantities of theintermediate resource type to be transferred into the plurality ofresource pools in the resource transfer network are further based onportions of a reservoir resource quantity assigned to the plurality ofselected resource paths.
 8. The method of claim 7, further comprising:monitoring a plurality of resource transfers on selected resource pathsin the resource transfer network; determining a net intermediateresource type quantity for each of the selected resource paths; anddetermining a reservoir resource quantity based on the net intermediateresource type quantity for each of the selected resource paths.
 9. Themethod of claim 8, wherein determining a net intermediate resource typequantity for a selected resource path comprises: determining a firstresult by reducing a total quantity of a front resource type that istransferred in at the start of a first half of the selected resourcepath by a total quantity of the front resource type that is transferredout at the end of a second half of the selected resource path; setting afirst net transfer amount to the absolute value of the first result whenthe first result is less than zero or setting the first net transferamount to zero when the first result is not less than zero; determininga second result by reducing a total quantity of a back resource typetransferred in at the start of the second half of the selected resourcepath by a total quantity of the back resource type that is transferredout at the end of the first half of the selected resource path; settinga second net transfer amount to the absolute value of the second resultwhen the second result is less than zero or setting the second nettransfer amount to zero when the second result is not less than zero;and summing the results of converting the first and second net transferamounts to amounts of the intermediate resource type to determine thenet intermediate resource type quantity for the selected resource path.10. The method of claim 8, further comprising adjusting the reservoirresource quantity based on the monitoring of the selected resource pathsin the resource transfer network.
 11. The method of claim 10, whereinthe reservoir resource quantity is increased when the monitoring of theselected resource paths indicates that a resource transfer on at leastone of the selected resource paths used a one-leg route with a costhigher than a threshold cost for the at least one of the selectedresource paths.
 12. The method of claim 10, wherein the reservoirresource quantity is decreased when the monitoring of the selectedresource paths indicates that a leg that can be used to form two-legroutes for a selected resource path was not used to form any routes forany resource transfers for the selected resource path during amonitoring period.
 13. The method of claim 7, wherein the monitoring ofthe selected resource paths is based on access to a network of resourcetracking computing devices.
 14. The method of claim 7, wherein themonitoring of the selected resource paths occurs over a monitoringperiod which occurs during a distribution period, and wherein theinstructions are generated and caused to be executed at the end of thedistribution period.
 15. The method of claim 8, wherein determining thequantity of an intermediate resource type to transfer into one of theplurality of resource pools in the resource transfer network that isassociated with a leg that can be part of a route with two legs for atleast one of the selected resource paths comprises: assigning a portionof the reservoir resource quantity to each of the selected resourcepaths; for each selected resource path: determining a total volume ofthe intermediate resource type that could be transferred across theselected resource path through routes formed using any legs with whichthe one of the plurality of resource pools is associated, excluding thevolume of the routes with costs higher than a threshold cost;determining a total volume of the intermediate resource type that couldbe transferred across the selected resource path through routes with twolegs formed using legs associated with any resource pools in theresource transfer network; dividing the total volume for the legsassociated with the one of the plurality of resource pools by the totalvolume for the legs associated with any resource pool to determine ashare for the one of the plurality of resource pools of the portion ofthe reservoir resource quantity assigned to the resource path; andmultiplying the share for the resource pool by the portion of thereservoir resource quantity assigned to the resource path to determinethe quantity of the intermediate resource type to transfer into the oneof the plurality of resource pools.
 16. A computer-implemented systemcomprising: a computing device adapted to monitor a plurality ofselected resource paths in a resource transfer network, determine aquantity of an intermediate resource type to transfer into each of aplurality of resource pools in the resource transfer network, each ofthe plurality of resource pools associated with at least one leg thatcan be part of a route with two legs for at least one of the selectedresource paths, and generate and cause to be executed instructionsdecrementing a register in a repository resource pool by the determinedquantities of the intermediate resource type to be transferred into theplurality of resource pools in the resource transfer network andincrementing a register in each of the plurality of resource pools inthe resource transfer network by the determined quantity of theintermediate resource type to be transferred into that resource poolwhen the determined quantity is greater than zero, wherein thedetermined quantities of the intermediate resource type to betransferred into the plurality of resource pools in the resourcetransfer network are further based on portions of a reservoir resourcequantity assigned to the plurality of selected resource paths.
 17. Thecomputer-implemented system of claim 16, wherein the computing device isfurther adapted to monitor a plurality of resource transfers on selectedresource paths in a resource transfer network, determine a netintermediate resource type quantity for each of the selected resourcepaths, and determine a reservoir resource quantity based on the netintermediate resource type quantity for each of the selected resourcepaths.
 18. The computer-implemented system of claim 17, wherein thecomputing device is further adapted to determine a net intermediateresource type quantity for a selected resource path by determining afirst result by reducing a total quantity of a front resource type thatis transferred in at the start of a first half of the selected resourcepath by a total quantity of the front resource type that is transferredout at the end of a second half of the selected resource path, setting afirst net transfer amount to the absolute value of the first result whenthe first result is less than zero or setting the first net transferamount to zero when the first result is not less than zero, determininga second result by reducing a total quantity of a back resource typetransferred in at the start of the second half of the selected resourcepath by a total quantity of the front resource type that is transferredout at the end of the first half of the selected resource path, settinga second net transfer amount to the absolute value of the second resultwhen the second result is less than zero or setting the second nettransfer amount to zero when the second result is not less than zero,summing the results of converting the first and second net transferamounts to amounts of the intermediate resource type to determine thenet intermediate resource type quantity for the selected resource path.19. The computer-implemented system of claim 16, wherein the computingdevice is further adapted to monitor the selected resource paths over amonitoring period which occurs during a distribution period, and whereinthe instructions are generated and caused to be executed at the end ofthe distribution period.
 20. The computer-implemented system of claim17, wherein the computing device is further adapted to determine thequantity of an intermediate resource type to transfer into one of theplurality of resource pools in the resource transfer network that isassociated with a leg that can be part of a route with two legs for atleast one of the selected resource paths by assigning a portion of thereservoir resource quantity to each of the selected resource paths, andfor each selected resource path, determining a total volume of theintermediate resource type that could be transferred across the selectedresource path through routes formed using any legs with which the one ofthe plurality of resource pools is associated, excluding the volume ofthe routes with costs higher than a threshold cost, determining a totalvolume of the intermediate resource type that could be transferredacross the selected resource path through routes with two legs formedusing legs associated with any resource pools in the resource transfernetwork, dividing the total volume for the legs associated with the oneof the plurality of resource pools by the total volume for the legsassociated with any resource pool to determine a share for the resourcepool of the portion of the reservoir resource quantity assigned to theresource path, and multiplying the share for the resource pool by theportion of the reservoir resource quantity assigned to the resource pathto determine the quantity of the intermediate resource type to transferinto the one of the plurality of resource pools.